Instrument adapter queries for external programs. #105
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When executing queries via the adapter, we may not recieve the instrumentation we expect. The ActiveRecord adapter uses a raw connection which bypasses the ActiveRecord instrumentation layer and instead talks directly to PG, making it impossible to know what queries are being executed.
This change cribs heavily from the implementation of the
log
method on theAbstractAdapter
class in ActiveRecord to make it easy to add instrumentation to an adapter. By default the instrumenter is set tonil
, and instrumentation will be a no-op; otherwise the query will be instrumented via theinstrument
method and passed the relevant payload to handle. The structure of this is deliberately similar to that of the event emitted by ActiveRecord'ssql.active_record
notification.